Potential fix for https://github.com/IgniteUI/igniteui-cli/security/code-scanning/39

To address the insecure randomness, replace all usage of Math.random() with a cryptographically secure random number generator. In browsers, this is window.crypto.getRandomValues(). Since this is TypeScript (and judging by the filename, probably browser code), use window.crypto.getRandomValues() to generate secure random numbers.

Update the getRandomNumber(min, max) implementation so that instead of relying on Math.random(), it uses a helper that generates a cryptographically strong random number in the needed range. Also replace all direct usages (in getRandomDate) of Math.random().

This requires:

1. Adding a helper function (e.g., secureRandomNumber(min, max)) that uses window.crypto.getRandomValues() to generate appropriate random integers in the [min, max] range (including both endpoints).
2. Replacing the implementation of getRandomNumber (and corresponding usages, and others as relevant) so that it uses the cryptographically secure logic throughout.
3. Only add new imports if absolutely required.

Edit only the relevant methods (getRandomNumber, getRandomDate) and do not change unrelated code.

Suggested fixes powered by Copilot Autofix. Review carefully before merging.